For the vuex actions. It makes sense to think of them as a chain of tasks that needs to be executed. This helps when it comes to naming, and it makes it easier to reason about them. Another thing is that the action that will be called from a component should describe the whole action chain.

For this action chain I can imagine something like this:
Name of the action chain (so the first action name): provisionExecutionToken
and the chain:

provisionExecutionToken(does encryption bit)
-> requestExecutionToken(does the server call bit, and then calls the js function to decrypt response)
-> setExecutionToken (mutation that sets the state)

It does not need to follow this exactly, but just wanted to give an example of what I am talking about.

@jongbonga and I had a session together to resolve the remaining conversations, with @Nghondzweni listening in. Thanks! 😊️

After that, I made to factor out a sealedPost helper substantially simplifies the action code: both encryptAndUploadFile and requestExecutionToken are now just small wrappers around it. @jongbonga and @longtomjr, can you review this change before merging?

Looks good. Thanks everyone for getting this sorted!